Planning and deploying service elements of a network service across transport and core network segments

ABSTRACT

The technologies described herein are generally directed to, in response to feature activation at an access point, planning and deploying service elements of a network service across transport and core network segments in a fifth generation (5G) network or other next generation networks. For example, a method described herein can include receiving a request to implement a network service in a network that includes access point equipment connected via a transport segment to a core network segment. The method can further include, based on the request, selecting deployment locations in the network for service elements to enable the network service, with an element of the service elements being selected to be deployed at a deployment location. Further, the method can include deploying the service element at the selected deployment location.

TECHNICAL FIELD

The subject application is related to different approaches to handlingnetwork services in networked computer systems and, for example, to theplanning and deploying of network service elements across networksegments.

BACKGROUND

As network implementations have continued to increase in size anddiversity, network services have increased in complexity. For somenetwork services, facilitating delivery of the service can entail thebroad deployment of service elements across disparate network segments,e.g., ranging from elements on the edge of access networks to coreequipment of the network. For each element, aspects of planning,provisioning, inventory, and activation can impact the time frame ofservice implementation.

Problems can occur when the pace of dynamic changes to network elementsconflicts with the timing and complexity of the implementation ofnetwork services.

BRIEF DESCRIPTION OF THE DRAWINGS

The technology described herein is illustrated by way of example and notlimited in the accompanying figures in which like reference numeralsindicate similar elements and in which:

FIG. 1 is an architecture diagram of an example system that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments.

FIG. 2 is a diagram of a non-limiting example system that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments.

FIG. 3 is a diagram of a non-limiting example system that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments.

FIG. 4 depicts a diagram of a non-limiting example system that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments.

FIG. 5 is a diagram of a non-limiting example system that can illustratenon-limiting examples of network services that can be planned andimplemented by one or more embodiments. For purposes of brevity,description of like elements and/or processes employed in otherembodiments is omitted.

FIG. 6 illustrates an example method that can facilitate, in response tofeature activation at an access point, planning and deploying serviceelements of a network service across transport and core networksegments.

FIG. 7 depicts a system that can facilitate, in response to featureactivation at an access point, planning and deploying service elementsof a network service across transport and core network segments.

FIG. 8 depicts an example non-transitory machine-readable medium thatcan include executable instructions that, when executed by a processorof a system, facilitate, in response to feature activation at an accesspoint, planning and deploying service elements of a network serviceacross transport and core network segments.

FIG. 9 illustrates an example block diagram of an example mobile handsetoperable to engage in a system architecture that can facilitateprocesses described herein, in accordance with one or more embodiments.

FIG. 10 illustrates an example block diagram of an example computeroperable to engage in a system architecture that can facilitateprocesses described herein, in accordance with one or more embodiments.

DETAILED DESCRIPTION

Generally speaking, one or more embodiments can facilitate, in responseto feature activation at an access point, planning and deploying serviceelements of a network service across transport and core networksegments. In addition, one or more embodiments described herein can bedirected towards a multi-connectivity framework that supports theoperation of new radio (NR, sometimes referred to as 5G). As will beunderstood, one or more embodiments can allow an integration of userdevices with network assistance, by supporting control and mobilityfunctionality on cellular links (e.g., long term evolution (LTE) or NR).One or more embodiments can provide benefits including, systemrobustness, reduced overhead, and global resource management, whilefacilitating direct communication links via a NR sidelink.

It should be understood that any of the examples and terms used hereinare non-limiting. For instance, while examples are generally directed tonon-standalone operation where the NR backhaul links are operating onmillimeter wave (mmWave) bands and the control plane links are operatingon sub-6 GHz LTE bands, it should be understood that it isstraightforward to extend the technology described herein to scenariosin which the sub-6 GHz anchor carrier providing control planefunctionality could also be based on NR. As such, any of the examplesherein are non-limiting examples, any of the embodiments, aspects,concepts, structures, functionalities or examples described herein arenon-limiting, and the technology may be used in various ways thatprovide benefits and advantages in radio communications in general.

In some embodiments the non-limiting terms “signal propagationequipment” or simply “propagation equipment,” “radio network node” orsimply “network node,” “radio network device,” “network device,” andaccess elements are used herein. These terms may be usedinterchangeably, and refer to any type of network node that can serveuser equipment and/or be connected to other network node or networkelement or any radio node from where user equipment can receive asignal. Examples of radio network node include, but are not limited to,base stations (BS), multi-standard radio (MSR) nodes such as MSR BS,gNodeB, eNode B, network controllers, radio network controllers (RNC),base station controllers (BSC), relay, donor node controlling relay,base transceiver stations (BTS), access points (AP), transmissionpoints, transmission nodes, remote radio units (RRU) (also termed radiounits herein), remote ratio heads (RRH), and nodes in distributedantenna system (DAS). Additional types of nodes are also discussed withembodiments below, e.g., donor node equipment and relay node equipment,an example use of these being in a network with an integrated accessbackhaul network topology.

In some embodiments, the non-limiting term user equipment (UE) is used.This term can refer to any type of wireless device that can communicatewith a radio network node in a cellular or mobile communication system.Examples of UEs include, but are not limited to, a target device, deviceto device (D2D) user equipment, machine type user equipment, userequipment capable of machine to machine (M2M) communication, PDAs,tablets, mobile terminals, smart phones, laptop embedded equipped (LEE),laptop mounted equipment (LME), USB dongles, and other equipment thatcan have similar connectivity. Example UEs are described further withFIGS. 9 and 10 below. Some embodiments are described in particular for5G new radio systems. The embodiments are however applicable to anyradio access technology (RAT) or multi-RAT system where the UEs operateusing multiple carriers, e.g., LTE.

The computer processing systems, computer-implemented methods, apparatusand/or computer program products described herein employ hardware and/orsoftware to solve problems that are highly technical in nature (e.g.,planning and deploying network services across a complicated and diversenetwork), that are not abstract and cannot be performed as a set ofmental acts by a human. For example, a human, or even a plurality ofhumans, cannot efficiently evaluate a multitude of deployment locationsin a small period of time, with the same level of accuracy and/orefficiency as the various embodiments described herein.

Aspects of the subject disclosure will now be described more fullyhereinafter with reference to the accompanying drawings in which examplecomponents, graphs and selected operations are shown. In the followingdescription, for purposes of explanation, numerous specific details areset forth in order to provide a thorough understanding of the variousembodiments. For example, some embodiments described can facilitate, inresponse to feature activation at an access point, planning anddeploying service elements of a network service across transport andcore network segments. Different examples that describe these aspectsare included with the description of FIGS. 1-10 below. It should benoted that the subject disclosure may be embodied in many differentforms and should not be construed as limited to this example or otherexamples set forth herein.

FIG. 1 is an architecture diagram of an example system 100 that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments. For purposes of brevity, description of like elementsand/or processes employed in other embodiments is omitted. It should benoted that, although many examples herein discuss particular types ofnetwork services (e.g., multimedia delivery and control planeestablishment/maintenance) embodiments described and suggested by thepresent disclosure are not limited by these examples. One having skillin the relevant art(s), given the description herein, appreciate thatmany types of network services that span transport and core segments ofa network, can be implemented based on the present disclosure.

As depicted, system 100 can include network equipment 150communicatively coupled to access point equipment 170 via network 190.In some examples, in response to access point equipment 170 having afeature activated, network equipment 150 can plan and deploy serviceelements of a network service across transport and core networksegments, e.g., as described with FIGS. 3-5 below.

Network equipment 150, in the example depicted, includes computerexecutable components 120, processor 160, storage device 162, and memory165. Computer executable components 120 can include condition detectingcomponent 122, location selecting component 124, deployment component126, and other components that can improve the operation of system 100as described or suggested by different embodiments described herein.

Further to the above, it should be appreciated that these components, aswell as aspects of the embodiments of the subject disclosure depicted inthis figure and various figures disclosed herein, are for illustrationonly, and as such, the architecture of such embodiments are not limitedto the systems, devices, and/or components depicted therein. Forexample, in some embodiments, network equipment 150 can further comprisevarious computer and/or computing-based elements described herein withreference to mobile handset 900 of FIG. 9 , and operating environment1000 of FIG. 10 . For example, one or more of the different functions ofnetwork equipment can be divided among various equipment, including, butnot limited to, including equipment at a central node global controllocated on the core Network, e.g., mobile edge computing (MEC),self-organized networks (SON), or RAN intelligent controller (RIC)network equipment.

In some embodiments, memory 165 can comprise volatile memory (e.g.,random access memory (RAM), static RAM (SRAM), dynamic RAM (DRAM), etc.)and/or non-volatile memory (e.g., read only memory (ROM), programmableROM (PROM), electrically programmable ROM (EPROM), electrically erasableprogrammable ROM (EEPROM), etc.) that can employ one or more memoryarchitectures. Further examples of memory 165 are described below withreference to system memory 1006 and FIG. 10 . Such examples of memory165 can be employed to implement any embodiments of the subjectdisclosure.

According to multiple embodiments, storage device 162 can include, butis not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, solid state drive (SSD) or other solid-state storagetechnology, Compact Disk Read Only Memory (CD ROM), digital video disk(DVD), blu-ray disk, or other optical disk storage, magnetic cassettes,magnetic tape, magnetic disk storage or other magnetic storage devices,or any other medium which can be used to store the desired informationand which can be accessed by the computer.

According to multiple embodiments, processor 160 can comprise one ormore processors and/or electronic circuitry that can implement one ormore computer and/or machine readable, writable, and/or executablecomponents and/or instructions that can be stored on memory 165. Forexample, processor 160 can perform various operations that can bespecified by such computer and/or machine readable, writable, and/orexecutable components and/or instructions including, but not limited to,logic, control, input/output (I/O), arithmetic, and/or the like. In someembodiments, processor 160 can comprise one or more componentsincluding, but not limited to, a central processing unit, a multi-coreprocessor, a microprocessor, dual microprocessors, a microcontroller, asystem on a chip (SOC), an array processor, a vector processor, andother types of processors. Further examples of processor 160 aredescribed below with reference to processing unit 1004 of FIG. 10 . Suchexamples of processor 160 can be employed to implement any embodimentsof the subject disclosure.

In one or more embodiments, computer executable components 120 can beused in connection with implementing one or more of the systems,devices, components, and/or computer-implemented operations shown anddescribed in connection with FIG. 1 or other figures disclosed herein.For example, in one or more embodiments, computer executable components120 can include instructions that, when executed by processor 160, canfacilitate performance of operations defining condition detectingcomponent 122. As discussed with FIGS. 4-5 below, condition detectingcomponent 122 can, in accordance with one or more embodiments, receive arequest to implement a network service in a network that includes accesspoint equipment connected via a transport segment to a core networksegment. For example, one or more embodiments of network equipment 150can receive a request from access point equipment 170 to implement anetwork service in a communications network with access point equipment170 connected via a transport segment to a core network segment (notshown).

Further, in another example, in one or more embodiments, computerexecutable components 120 can include instructions that, when executedby processor 160, can facilitate performance of operations defininglocation selecting component 124. As discussed with FIGS. 3-4 below,location selecting component 124 can, in accordance with one or moreembodiments, based on the request to implement a network service, selectdeployment locations in the network for service elements to enable thenetwork service. For example, in one or more embodiments, networkequipment 150 can utilize location selecting component 124 to, based onthe request from access point equipment 170, select deployment locationsin the network for service elements to enable the network service.

In yet another example, computer executable components 120 can includeinstructions that, when executed by processor 160, can facilitateperformance of operations defining deployment component 126. Asdiscussed herein, deployment component 126 can facilitate deploying theservice element at the selected deployment location. For example, in acircumstance where the service request includes a network multimediaservice (e.g., discussed with FIG. 4 below), one or more embodiments ofnetwork equipment 150 can utilize deployment component 126 to facilitatedeploying a service element at the selected deployment location.

FIG. 2 is a diagram of a non-limiting example system 200 that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments. For purposes of brevity, description of like elementsand/or processes employed in other embodiments is omitted. As discussedfurther below, system 200 can include access point equipment 170connected to network equipment 150 via network 190.

As depicted, access point equipment 170 can include computer executablecomponents 220, processor 260, storage device 262, and memory 265 whichcan perform functions similar to computer executable components 120,processor 160, storage device 162, and memory 165 described with FIG. 1above. Particularly, memory 265 that can store one or more computerand/or machine readable, writable, and/or executable components and/orinstructions 220 that, when respectively executed by processor 260, canfacilitate performance of operations defined by the executablecomponent(s) and/or instruction(s).

Generally, applications (e.g., computer executable components 220) caninclude routines, programs, components, data structures, etc., thatperform particular tasks or implement particular abstract data types. Insystem 200, computer executable components 220 can include statuscomponent 212, service interface component 214, and other componentsdescribed or suggested by different embodiments described herein thatcan improve the operation of system 200. It should be appreciated thatthese components, as well as aspects of the embodiments of the subjectdisclosure depicted in this figure and various figures disclosed herein,are for illustration only, and as such, the architecture of suchembodiments are not limited to the systems, devices, and/or componentsdepicted therein. For example, in some embodiments, access pointequipment 170 can further comprise various computer and/orcomputing-based elements described herein with reference to mobilehandset 900 of FIG. 9 and operating environment 1000 described with FIG.10 .

In an example, in one or more embodiments, computer executablecomponents 220 can be used in connection with implementing one or moreof the systems, devices, components, and/or computer-implementedoperations shown and described in connection with FIG. 2 or otherfigures disclosed herein. For example, in one or more embodiments,computer executable components 220 can include instructions that, whenexecuted by processor 260, can facilitate performance of operationsdefining status component 212. As discussed with FIGS. 4-5 below, in oneor more embodiments, status component 212 can communicate a request to alogical service system to implement a logical service in acommunications network, with the access point equipment being connectedby a transport section of the communications network to a core sectionof the communications network.

For example, in one or more embodiments, access point equipment 170 canutilize status component 212 to communicate a request to a networkequipment 150, where computer executable components 120 can implement alogical service system, e.g., via condition detecting component 122,location selecting component 124, and deployment component 126. Further,as described with FIGS. 4-5 below, access point equipment 170 can beconnected by a transport section of a network to a core section of thecommunications network.

In another example, in one or more embodiments, computer executablecomponents 220 can include instructions that, when executed by processor160, can facilitate performance of operations defining, serviceinterface component 214. As discussed with FIGS. 4-5 below, serviceinterface component 214 can, in accordance with one or more embodiments,receive, from the logical service system, an indication that the logicalservice is available for use, with the logical service beinginstantiated by logical service elements deployed at transport equipmentcomprised in the transport section, and core equipment comprised in thecore section, and with the transport equipment and the core equipmentwere selected by the logical service system based on a requirement ofthe logical service. For example, in one or more embodiments, accesspoint equipment 170 can receive via service interface component 214,from network equipment 150, an indication that the multimedia service isavailable for use. In this example, the multimedia service can have beeninstantiated by logical service elements deployed at transport equipmentselected by deployment component 126. Example logical service elementsfor different example network services are discussed below with FIG. 4(e.g., a multimedia delivery service), and FIG. 5 (e.g., a control planeservice).

FIG. 3 is a diagram of a non-limiting example system 300 that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments. For purposes of brevity, description of like elementsand/or processes employed in other embodiments is omitted.

As depicted, in accordance with one of more embodiments, system 300shows two phases of design and implementation of network services acommunications network, e.g., discovery phase 302 and planning phase 303for a communication network that includes RAN 391 with access pointequipment 170, transport segment 393, and core equipment 394. Thediagram further illustrates a network service slice with allocatedresources 395A-E overlayed on existing network parts noted above.Discovery phase 302 includes discover 365, inventory 375, monitor 382,and troubleshoot 385, and planning phase 303 includes plan 310,inventory 330, monitor 350, and troubleshoot 360, in accordance with oneor more embodiments. For discovery phase 302 and planning phase 303, aservice design activity includes provision 320 and 370, and a serviceimplementation activity includes configure/activate 340 and 380,respectively.

One or more embodiments can work within a cloud platform environment tocoordinate the planning and deployment of network services acrossmultiple domains (e.g., segments or parts) of a communications network,e.g., the RAN segment connected to network core equipment via atransport segment. One approach to planning and deploying can utilizenetwork slices to utilize existing network resources, e.g., can overlaynetwork services (e.g., logical services).

Using different approaches, one or more embodiments can facilitate theabstraction of network services into network slices managed by theprovider of the network. In one or more embodiments, a network slice candescribe a virtual network with independent sets of logical networkfunctions that can be selected to support particular requirements ofdifferent network services, e.g., allocated resources 395A-E. One ormore embodiments can request allocation of a network slice havingcertain characteristics selected to facilitate successful programexecution. Example characteristics of network slices can include, butare not limited to, location, speed, connectivity, latency, security,energy use, coverage, and capacity.

In an example implementation, a virtual network function for a networkservice can be deployed by using an existing instance of the virtualnetwork function at a selected deployment location. In another example,when an existing instance of a virtual network function is notavailable, one or more embodiments can instantiate the virtual networkfunction at a deployment location. As described herein, network servicescan be implemented by service elements linked across different networkelements, e.g., allocated resources 395A-E linked into a network slice.

Returning to the example depicted, in one or more embodiments, indiscovery phase 302, discovery process 390 can be used to gather currentinformation about different segments of the communication network, e.g.,by linked processes including, but not limited to, inventory 375,monitor 382, and troubleshoot 385.

With inventory 375 process, an inventory record of the service designcan be stored. It should be noted that, for example network servicesdescribed herein, to plan implementation of the function across thedifferent segments, a network active inventory and thelogical/infrastructure connectivity of the network can be used todetermine where and how different network service elements are deployedand linked. Once gathered, this information can be used in planningphase 303, by linked processes including, but not limited to, plan 310,inventory 330, monitor 350, and troubleshoot 360, in accordance with oneor more embodiments.

FIG. 4 depicts a diagram of a non-limiting example system 400 that canfacilitate, in response to feature activation at an access point,planning and deploying service elements of a network service acrosstransport and core network segments, in accordance with one or moreembodiments. For purposes of brevity, description of like elementsand/or processes employed in other embodiments is omitted.

An example network service that can be implemented using one or moreembodiments described herein is a broadcast/multicast multimedia servicecapability. In some implementations, this service can be comprised oflinked network service elements spanning multiple broad networksegments, e.g., mobility RAN 430, access point equipment 170 (e.g., viaan eNodeB 437), transport segment 420, and core equipment 410, with acombination of multiple physical and virtual network functions beingused to implement the service.

In this example, the feature activation of access point equipment 170can be activation of a multimedia coordination function by eNodeB 437,and condition detecting component 122 of network equipment 150 can beconfigured to operate as a notification listener to receive networkelement notifications, e.g., from a cloud service provider. Based on thefunction activation, in an example implementation, at core equipment410, multimedia gateway 490 can be implemented for functions such assession management and traffic routing, with a multicast router 412 toprovide overlay connectivity to transport segment 420 where the dataflows in and out the RAN 430. In this example, to facilitateconnectivity between core equipment 410 and transport segment 420, oneor more embodiments can plan and implement a routing encapsulationtunnel 450 to support the multi-cast/uni-cast traffic flow.

One or more embodiments can plan and implement complex combinations ofservice elements, e.g., including, but not limited to, multimediagateway 490, multicast router 412, routing encapsulation tunnel 450,multiservice nodes (MSN) 415A-V, and integrated access router 435.

FIG. 5 is a diagram of a non-limiting example system 500 that canillustrate non-limiting examples of network services that can be plannedand implemented by one or more embodiments. For purposes of brevity,description of like elements and/or processes employed in otherembodiments is omitted.

Depicted in FIG. 5 , RAN 391 includes access point equipment 170,transport segment 393, and core equipment 394, and can be used todescribe additional network services that can be deployed by one or moreembodiments. As also depicted, access management function clusters510A-B are communicatively coupled to core equipment 394 and accessmanagement function clusters 510A was logically coupled via an exampleN2 interface 495 to access point equipment 170.

Another example network service that can be implemented by one or moreembodiments is a service to connect access point equipment 170 to acontrol plane, e.g., establishing and maintaining an N2 interface 520connection between access point equipment 170 (e.g., eNodeB 437) to atleast one of access management function clusters 510A-B for controlplane resource allocation. It should be appreciated that, although thisexample concerns the N2 interface of fifth generation networktechnologies, other similar services can be implemented with aspects ofembodiments discussed herein, e.g., including, but not limited to, othertypes of coordinated interface between edge network elements and centralnetwork elements.

As discussed above, embodiments can be triggered, in accordance with oneor more embodiments, by condition detecting component 122 detecting arequest (or any other indication) to implement a network service byother network equipment. In this example, a function request can includeaccess point equipment 170 requesting access management functioninformation.

Based on the request (e.g., function activation), in discovery phase302, network equipment 150 can use discovery process 390 to discoveraccess management function clusters 510A-B as sources of accessmanagement function information. Once discovered, at planning phase 303,embodiments can evaluate (e.g., via location selecting component 124)different access management function clusters 510A-B as potentialsources of access management function information, e.g., by receivingand evaluating different control plane configurations of accessmanagement function clusters 510A-B.

In an approach to evaluation that can be used to evaluate accessmanagement function clusters 510A-B, a service design workflow can begenerated to evaluate access management function clusters 510A-B.Criteria that can be used for evaluation include the physical distancesof paths from access point equipment 170 to access management functionclusters 510A-B, with an advantageous cluster having the shortestdistance of access management function clusters 510A-B. Once selected,deployment component 126 can configure access point equipment 170 toaccess the management functions from one or more access managementfunction clusters 510A-B.

Another example network service that can be implemented by one or moreembodiments is a user plane function service to establish user planefunction 555 between cloud service provider platform 580 and userequipment 590. It should be appreciated that, although this exampleconcerns a user plane function that is an element of fifth generationnetwork technologies, other similar services can be implemented withaspects of embodiments discussed herein, e.g., including, but notlimited to, other types of virtual private network connections betweencore network equipment and customer equipment.

In an example implementation, one or more embodiments can use a networkslice that includes network resources 395A-E to enable user planefunction 555 across the depicted network segments. In one or moreembodiments, different functions of network equipment 150 can be a partof network operational support systems, and for certain types ofcustomers, before instantiation of user plane 555, network businesssupport systems can be queried to verify the order from the customer,e.g., by validating network the slice service contract for resources395A-E, for the cloud service provider of cloud service providerplatform 580.

As discussed above, embodiments can be triggered, in accordance with oneor more embodiments, by condition detecting component 122 detecting arequest (or any other indication) to implement a network service byother network equipment. In this example, a function request can includeaccess point equipment 170 requesting establishment of user plane 555via a user plane management function service for a connection betweencloud service provider platform 580 and user equipment 590. Examplesources of this request include cloud service provider compute hosts orother elements that can utilize user plane communications.

Based on the request (e.g., function activation), in discovery phase302, network equipment 150 can use discovery process 390 to evaluate aninventory view of the resources and locations of resources of RAN 391,transport segment 393, and core equipment 394. Example resources caninclude parts of the virtual machine-based architecture of cloud serviceprovider platform 580 and cloud service provider compute hosts (notdepicted).

Once discovered, at planning phase 303, embodiments can evaluate (e.g.,via location selecting component 124) discovered elements of the system.In an approach to evaluation that can be used to evaluate accessmanagement function clusters 510A-B, a service design workflow can begenerated to evaluate different resources to be used by user plane 555,and once selected, deployment component 126 can configure theseresources to provide the network service.

FIG. 6 illustrates an example method 600 that can facilitate, inresponse to feature activation at an access point, planning anddeploying service elements of a network service across transport andcore network segments, in accordance with one or more embodiments. Forpurposes of brevity, description of like elements and/or processesemployed in other embodiments is omitted.

At 602, method 600 can include receiving a request to implement anetwork service in a network that includes access point equipmentconnected via a transport segment to a core network segment. Forexample, in one or more embodiments, a method can include receiving arequest to implement a multimedia service (e.g., from multimedia gateway490 of FIG. 4 ) in a network that includes access point equipment 170connected via transport segment 420 to a core network segment (e.g., tocore equipment 410).

At 604, method 600 can include, based on the request, selectingdeployment locations in the network for service elements to enable thenetwork service, with an element of the service elements being selectedto be deployed at a deployment location. For example, one or moreembodiments can, based on the request, select deployment locations(e.g., MSNs 415A-B, integrated access router 435) in the network forservice elements to enable the network service, with an element of theservice elements being selected to be deployed at a deployment location.

At 606, method 600 can include facilitate deploying the service elementat the selected deployment location. For example, in one or moreembodiments, facilitate deploying the service element at the selecteddeployment location, e.g., selected via location selecting component124.

FIG. 7 depicts a system 700 that can facilitate, in response to featureactivation at an access point, planning and deploying service elementsof a network service across transport and core network segments, inaccordance with one or more embodiments. For purposes of brevity,description of like elements and/or processes employed in otherembodiments is omitted. As depicted, system 700 can include conditiondetecting component 122, location selecting component 124, deploymentcomponent 126, and other components described or suggested by differentembodiments described herein, that can improve the operation of system700.

In an example, component 702 can include the functions of conditiondetecting component 122, supported by the other layers of system 700.For example, component 702 can receive a request to implement a networkservice in a network that includes access point equipment connected viaa transport segment to a core network segment. For example, one or moreembodiments condition detecting component 122 can receive a request toimplement a network service in a network that includes access pointequipment 170 connected via a transport segment to a core equipment 410.

In this and other examples, component 704 can include the functions oflocation selecting component 124, supported by the other layers ofsystem 700. Continuing this example, in one or more embodiments,component 704 can, based on the request, can select deployment locationsin the network for service elements to enable the network service, withan element of the service elements being selected to be deployed at adeployment location. For example, one or more embodiments can, based onthe request, location selecting component 124 can select deploymentlocations in the network for service elements to enable the networkservice.

In an example, component 706 can include the functions of deploymentcomponent 126, supported by the other layers of system 700. For example,component 706 can facilitate deploying the service element at theselected deployment location. For example, in one or more embodiments,deployment component 126 of network equipment 150 can facilitatedeploying the service element at the selected deployment location.

FIG. 8 depicts an example 800 non-transitory machine-readable medium 810that can include executable instructions that, when executed by aprocessor of a system, facilitate, in response to feature activation atan access point, planning and deploying service elements of a networkservice across transport and core network segments, in accordance withone or more embodiments described above. For purposes of brevity,description of like elements and/or processes employed in otherembodiments is omitted. As depicted, non-transitory machine-readablemedium 810 includes executable instructions that can facilitateperformance of operations 802-808.

In one or more embodiments, the operations can include operation 802that can receive a request to implement a network service in a networkthat includes access point equipment connected via a transport segmentto a core network segment. For example, one or more embodiments anoperation can receive a request to implement a network service in anetwork that includes access point equipment 170 connected via atransport segment to a core equipment 410.

In one or more embodiments, the operations can include operation 804that can, based on the request, can select deployment locations in thenetwork for service elements to enable the network service, with anelement of the service elements being selected to be deployed at adeployment location. For example, one or more embodiments can, based onthe request, location selecting component 124 can select deploymentlocations in the network for service elements to enable the networkservice. In an additional example, component 806 can facilitatedeploying the service element at the selected deployment location.

FIG. 9 illustrates an example block diagram of an example mobile handset900 operable to engage in a system architecture that facilitateswireless communications according to one or more embodiments describedherein. Although a mobile handset is illustrated herein, it will beunderstood that other devices can be a mobile device, and that themobile handset is merely illustrated to provide context for theembodiments of the various embodiments described herein. The followingdiscussion is intended to provide a brief, general description of anexample of a suitable environment in which the various embodiments canbe implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the embodimentsalso can be implemented in combination with other program modules and/oras a combination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, solid statedrive (SSD) or other solid-state storage technology, Compact Disk ReadOnly Memory (CD ROM), digital video disk (DVD), Blu-ray disk, or otheroptical disk storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe computer. In this regard, the terms “tangible” or “non-transitory”herein as applied to storage, memory or computer-readable media, are tobe understood to exclude only propagating transitory signals per se asmodifiers and do not relinquish rights to all standard storage, memoryor computer-readable media that are not only propagating transitorysignals per se.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media

The handset includes a processor 902 for controlling and processing allonboard operations and functions. A memory 904 interfaces to theprocessor 902 for storage of data and one or more applications 906(e.g., a video player software, user feedback component software, etc.).Other applications can include voice recognition of predetermined voicecommands that facilitate initiation of the user feedback signals. Theapplications 906 can be stored in the memory 904 and/or in a firmware908, and executed by the processor 902 from either or both the memory904 or/and the firmware 908. The firmware 908 can also store startupcode for execution in initializing the handset 900. A communicationscomponent 910 interfaces to the processor 902 to facilitatewired/wireless communication with external systems, e.g., cellularnetworks, VoIP networks, and so on. Here, the communications component910 can also include a suitable cellular transceiver 911 (e.g., a GSMtransceiver) and/or an unlicensed transceiver 913 (e.g., Wi-Fi, WiMax)for corresponding signal communications. The handset 900 can be a devicesuch as a cellular telephone, a PDA with mobile communicationscapabilities, and messaging-centric devices. The communicationscomponent 910 also facilitates communications reception from terrestrialradio networks (e.g., broadcast), digital satellite radio networks, andInternet-based radio services networks

The handset 900 includes a display 912 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 912 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 912 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface914 is provided in communication with the processor 902 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1294) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 900, for example. Audio capabilities areprovided with an audio I/O component 916, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 916 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 900 can include a slot interface 918 for accommodating a SIC(Subscriber Identity Component) in the form factor of a card SIM oruniversal SIM 920, and interfacing the SIM card 920 with the processor902. However, it is to be appreciated that the SIM card 920 can bemanufactured into the handset 900, and updated by downloading data andsoftware.

The handset 900 can process IP data traffic through the communicationscomponent 910 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 900 and IP-based multimediacontent can be received in either an encoded or a decoded format.

A video processing component 922 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 922can aid in facilitating the generation, editing, and sharing of videoquotes. The handset 900 also includes a power source 924 in the form ofbatteries and/or an AC power subsystem, which power source 924 caninterface to an external power system or charging equipment (not shown)by a power I/O component 926.

The handset 900 can also include a video component 930 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 930 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 932 facilitates geographically locating the handset 900. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 934facilitates the user initiating the quality feedback signal. The userinput component 934 can also facilitate the generation, editing andsharing of video quotes. The user input component 934 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 906, a hysteresis component 936facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 938 can be provided that facilitatestriggering of the hysteresis component 936 when the Wi-Fi transceiver913 detects the beacon of the access point. A SIP client 940 enables thehandset 900 to support SIP protocols and register the subscriber withthe SIP registrar server. The applications 906 can also include a client942 that provides at least the capability of discovery, play and storeof multimedia content, for example, music.

The handset 900, as indicated above related to the communicationscomponent 910, includes an indoor network radio transceiver 913 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 900. The handset 900 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Network 190 can employ various cellular systems, technologies, andmodulation schemes to facilitate wireless radio communications betweendevices. While example embodiments include use of 5G new radio (NR)systems, one or more embodiments discussed herein can be applicable toany radio access technology (RAT) or multi-RAT system, including whereuser equipment operate using multiple carriers, e.g., LTE FDD/TDD,GSM/GERAN, CDMA2000, etc. For example, wireless communication system 200can operate in accordance with global system for mobile communications(GSM), universal mobile telecommunications service (UMTS), long termevolution (LTE), LTE frequency division duplexing (LTE FDD, LTE timedivision duplexing (TDD), high speed packet access (HSPA), code divisionmultiple access (CDMA), wideband CDMA (WCMDA), CDMA2000, time divisionmultiple access (TDMA), frequency division multiple access (FDMA),multi-carrier code division multiple access (MC-CDMA), single-carriercode division multiple access (SC-CDMA), single-carrier FDMA (SC-FDMA),orthogonal frequency division multiplexing (OFDM), discrete Fouriertransform spread OFDM (DFT-spread OFDM) single carrier FDMA (SC-FDMA),Filter bank based multi-carrier (FBMC), zero tail DFT-spread-OFDM (ZTDFT-s-OFDM), generalized frequency division multiplexing (GFDM), fixedmobile convergence (FMC), universal fixed mobile convergence (UFMC),unique word OFDM (UW-OFDM), unique word DFT-spread OFDM (UWDFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM, resource-block-filteredOFDM, Wi Fi, WLAN, WiMax, and the like. However, various features andfunctionalities of system 100 are particularly described wherein thedevices of system 100 are configured to communicate wireless signalsusing one or more multi carrier modulation schemes, wherein data symbolscan be transmitted simultaneously over multiple frequency subcarriers(e.g., OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). Theembodiments are applicable to single carrier as well as to multicarrier(MC) or carrier aggregation (CA) operation of the user equipment. Theterm carrier aggregation (CA) is also called (e.g., interchangeablycalled) “multi-carrier system”, “multi-cell operation”, “multi-carrieroperation”, “multi-carrier” transmission and/or reception. Note thatsome embodiments are also applicable for Multi RAB (radio bearers) onsome carriers (that is data plus speech is simultaneously scheduled).

Various embodiments described herein can be configured to provide andemploy 5G wireless networking features and functionalities. With 5Gnetworks that may use waveforms that split the bandwidth into severalsub bands, different types of services can be accommodated in differentsub bands with the most suitable waveform and numerology, leading toimproved spectrum utilization for 5G networks. Notwithstanding, in themmWave spectrum, the millimeter waves have shorter wavelengths relativeto other communications waves, whereby mmWave signals can experiencesevere path loss, penetration loss, and fading. However, the shorterwavelength at mmWave frequencies also allows more antennas to be packedin the same physical dimension, which allows for large-scale spatialmultiplexing and highly directional beamforming.

FIG. 10 provides additional context for various embodiments describedherein, intended to provide a brief, general description of a suitableoperating environment 1000 in which the various embodiments of theembodiment described herein can be implemented. While the embodimentshave been described above in the general context of computer-executableinstructions that can run on one or more computers, those skilled in theart will recognize that the embodiments can be also implemented incombination with other program modules and/or as a combination ofhardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, Internet of Things (IoT)devices, distributed computing systems, as well as personal computers,hand-held computing devices, microprocessor-based or programmableconsumer electronics, and the like, each of which can be operativelycoupled to one or more associated devices.

The illustrated embodiments of the embodiments herein can be alsopracticed in distributed computing environments where certain tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules can be located in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media, machine-readable storage media,and/or communications media, which two terms are used herein differentlyfrom one another as follows. Computer-readable storage media ormachine-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media or machine-readablestorage media can be implemented in connection with any method ortechnology for storage of information such as computer-readable ormachine-readable instructions, program modules, structured data orunstructured data.

Computer-readable storage media can include, but are not limited to,random access memory (RAM), read only memory (ROM), electricallyerasable programmable read only memory (EEPROM), flash memory or othermemory technology, compact disk read only memory (CD-ROM), digitalversatile disk (DVD), Blu-ray disc (BD) or other optical disk storage,magnetic cassettes, magnetic tape, magnetic disk storage or othermagnetic storage devices, solid state drives or other solid statestorage devices, or other tangible and/or non-transitory media which canbe used to store desired information. In this regard, the terms“tangible” or “non-transitory” herein as applied to storage, memory orcomputer-readable media, are to be understood to exclude onlypropagating transitory signals per se as modifiers and do not relinquishrights to all standard storage, memory or computer-readable media thatare not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local orremote computing devices, e.g., via access requests, queries or otherdata retrieval protocols, for a variety of operations with respect tothe information stored by the medium.

Communications media typically embody computer-readable instructions,data structures, program modules or other structured or unstructureddata in a data signal such as a modulated data signal, e.g., a carrierwave or other transport mechanism, and includes any information deliveryor transport media. The term “modulated data signal” or signals refersto a signal that has one or more of its characteristics set or changedin such a manner as to encode information in one or more signals. By wayof example, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 10 , the example operating environment 1000for implementing various embodiments of the aspects described hereinincludes a computer 1002, the computer 1002 including a processing unit1004, a system memory 1006 and a system bus 1008. The system bus 1008couples system components including, but not limited to, the systemmemory 1006 to the processing unit 1004. The processing unit 1004 can beany of various commercially available processors. Dual microprocessorsand other multi-processor architectures can also be employed as theprocessing unit 1004.

The system bus 1008 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1006includes ROM 1010 and RAM 1012. A basic input/output system (BIOS) canbe stored in a non-volatile memory such as ROM, erasable programmableread only memory (EPROM), EEPROM, which BIOS contains the basic routinesthat help to transfer information between elements within the computer1002, such as during startup. The RAM 1012 can also include a high-speedRAM such as static RAM for caching data.

The computer 1002 further includes an internal hard disk drive (HDD)1014 (e.g., EIDE, SATA), one or more external storage devices 1016(e.g., a magnetic floppy disk drive (FDD) 1016, a memory stick or flashdrive reader, a memory card reader, etc.) and a drive 1020, e.g., suchas a solid-state drive, an optical disk drive, which can read or writefrom a disk 1022, such as a CD-ROM disc, a DVD, a BD, etc.Alternatively, where a solid-state drive is involved, disk 1022 wouldnot be included, unless separate. While the internal HDD 1014 isillustrated as located within the computer 1002, the internal HDD 1014can also be configured for external use in a suitable chassis (notshown). Additionally, while not shown in environment 1000, a solid-statedrive (SSD) could be used in addition to, or in place of, an HDD 1014.The HDD 1014, external storage device(s) 1016 and drive 1020 can beconnected to the system bus 1008 by an HDD interface 1024, an externalstorage interface 1026 and a drive interface 1028, respectively. Theinterface 1024 for external drive implementations can include at leastone or both of Universal Serial Bus (USB) and Institute of Electricaland Electronics Engineers (IEEE) 1394 interface technologies. Otherexternal drive connection technologies are within contemplation of theembodiments described herein.

The drives and their associated computer-readable storage media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1002, the drives andstorage media accommodate the storage of any data in a suitable digitalformat. Although the description of computer-readable storage mediaabove refers to respective types of storage devices, it should beappreciated by those skilled in the art that other types of storagemedia which are readable by a computer, whether presently existing ordeveloped in the future, could also be used in the example operatingenvironment, and further, that any such storage media can containcomputer-executable instructions for performing the methods describedherein.

A number of program modules can be stored in the drives and RAM 1012,including an operating system 1030, one or more application programs1032, other program modules 1034 and program data 1036. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1012. The systems and methods described herein can beimplemented utilizing various commercially available operating systemsor combinations of operating systems.

Computer 1002 can optionally comprise emulation technologies. Forexample, a hypervisor (not shown) or other intermediary can emulate ahardware environment for operating system 1030, and the emulatedhardware can optionally be different from the hardware illustrated inFIG. 10 . In such an embodiment, operating system 1030 can comprise onevirtual machine (VM) of multiple VMs hosted at computer 1002.Furthermore, operating system 1030 can provide runtime environments,such as the Java runtime environment or the .NET framework, forapplications 1032. Runtime environments are consistent executionenvironments that allow applications 1032 to run on any operating systemthat includes the runtime environment. Similarly, operating system 1030can support containers, and applications 1032 can be in the form ofcontainers, which are lightweight, standalone, executable packages ofsoftware that include, e.g., code, runtime, system tools, systemlibraries and settings for an application.

Further, computer 1002 can be enable with a security module, such as atrusted processing module (TPM). For instance, with a TPM, bootcomponents hash next in time boot components, and wait for a match ofresults to secured values, before loading a next boot component. Thisprocess can take place at any layer in the code execution stack ofcomputer 1002, e.g., applied at the application execution level or atthe operating system (OS) kernel level, thereby enabling security at anylevel of code execution.

A user can enter commands and information into the computer 1002 throughone or more wired/wireless input devices, e.g., a keyboard 1038, a touchscreen 1040, and a pointing device, such as a mouse 1042. Other inputdevices (not shown) can include a microphone, an infrared (IR) remotecontrol, a radio frequency (RF) remote control, or other remote control,a joystick, a virtual reality controller and/or virtual reality headset,a game pad, a stylus pen, an image input device, e.g., camera(s), agesture sensor input device, a vision movement sensor input device, anemotion or facial detection device, a biometric input device, e.g.,fingerprint or iris scanner, or the like. These and other input devicesare often connected to the processing unit 1004 through an input deviceinterface 1044 that can be coupled to the system bus 1008, but can beconnected by other interfaces, such as a parallel port, an IEEE 1394serial port, a game port, a USB port, an IR interface, a BLUETOOTH®interface, etc.

A monitor 1046 or other type of display device can be also connected tothe system bus 1008 via an interface, such as a video adapter 1048. Inaddition to the monitor 1046, a computer typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1002 can operate in a networked environment using logicalconnections via wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1050. The remotecomputer(s) 1050 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentappliance, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer1002, although, for purposes of brevity, only a memory/storage device1052 is illustrated. The logical connections depicted includewired/wireless connectivity to a local area network (LAN) 1054 and/orlarger networks, e.g., a wide area network (WAN) 1056. Such LAN and WANnetworking environments are commonplace in offices and companies, andfacilitate enterprise-wide computer networks, such as intranets, all ofwhich can connect to a global communications network, e.g., theInternet.

When used in a LAN networking environment, the computer 1002 can beconnected to the local network 1054 through a wired and/or wirelesscommunication network interface or adapter 1058. The adapter 1058 canfacilitate wired or wireless communication to the LAN 1054, which canalso include a wireless access point (AP) disposed thereon forcommunicating with the adapter 1058 in a wireless mode.

When used in a WAN networking environment, the computer 1002 can includea modem 1060 or can be connected to a communications server on the WAN1056 via other means for establishing communications over the WAN 1056,such as by way of the Internet. The modem 1060, which can be internal orexternal and a wired or wireless device, can be connected to the systembus 1008 via the input device interface 1044. In a networkedenvironment, program modules depicted relative to the computer 1002 orportions thereof, can be stored in the remote memory/storage device1052. It will be appreciated that the network connections shown areexample and other means of establishing a communications link betweenthe computers can be used.

When used in either a LAN or WAN networking environment, the computer1002 can access cloud storage systems or other network-based storagesystems in addition to, or in place of, external storage devices 1016 asdescribed above, such as but not limited to a network virtual machineproviding one or more aspects of storage or processing of information.Generally, a connection between the computer 1002 and a cloud storagesystem can be established over a LAN 1054 or WAN 1056 e.g., by theadapter 1058 or modem 1060, respectively. Upon connecting the computer1002 to an associated cloud storage system, the external storageinterface 1026 can, with the aid of the adapter 1058 and/or modem 1060,manage storage provided by the cloud storage system as it would othertypes of external storage. For instance, the external storage interface1026 can be configured to provide access to cloud storage sources as ifthose sources were physically connected to the computer 1002.

The computer 1002 can be operable to communicate with any wirelessdevices or entities operatively disposed in wireless communication,e.g., a printer, scanner, desktop and/or portable computer, portabledata assistant, communications satellite, any piece of equipment orlocation associated with a wirelessly detectable tag (e.g., a kiosk,news stand, store shelf, etc.), and telephone. This can include WirelessFidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, thecommunication can be a predefined structure as with a conventionalnetwork or simply an ad hoc communication between at least two devices.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

Further to the description above, as it employed in the subjectspecification, the term “processor” can refer to substantially anycomputing processing unit or device comprising, but not limited tocomprising, single-core processors; single-processors with softwaremultithread execution capability; multi-core processors; multi-coreprocessors with software multithread execution capability; multi-coreprocessors with hardware multithread technology; parallel platforms; andparallel platforms with distributed shared memory. Additionally, aprocessor can refer to an integrated circuit, an application specificintegrated circuit (ASIC), a digital signal processor (DSP), a fieldprogrammable gate array (FPGA), a programmable logic controller (PLC), acomplex programmable logic device (CPLD), a discrete gate or transistorlogic, discrete hardware components, or any combination thereof designedto perform the functions described herein. Processors can exploitnano-scale architectures such as, but not limited to, molecular andquantum-dot based transistors, switches and gates, in order to optimizespace usage or enhance performance of user equipment. A processor mayalso be implemented as a combination of computing processing units.

In the subject specification, terms such as “store,” “storage,” “datastore,” data storage,” “database,” and substantially any otherinformation storage component relevant to operation and functionality ofa component, refer to “memory components,” or entities embodied in a“memory” or components comprising the memory. It will be appreciatedthat the memory components described herein can be either volatilememory or nonvolatile memory, or can include both volatile andnonvolatile memory.

As used in this application, the terms “component,” “system,”“platform,” “layer,” “selector,” “interface,” and the like are intendedto refer to a computer-related entity or an entity related to anoperational apparatus with one or more specific functionalities, whereinthe entity can be either hardware, a combination of hardware andsoftware, software, or software in execution. As an example, a componentmay be, but is not limited to being, a process running on a processor, aprocessor, an object, an executable, a thread of execution, a program,and/or a computer. By way of illustration and not limitation, both anapplication running on a server and the server can be a component. Oneor more components may reside within a process and/or thread ofexecution and a component may be localized on one computer and/ordistributed between two or more computers. In addition, these componentscan execute from various computer readable media, device readablestorage devices, or machine-readable media having various datastructures stored thereon. The components may communicate via localand/or remote processes such as in accordance with a signal having oneor more data packets (e.g., data from one component interacting withanother component in a local system, distributed system, and/or across anetwork such as the Internet with other systems via the signal). Asanother example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, which is operated by a software or firmwareapplication executed by a processor, wherein the processor can beinternal or external to the apparatus and executes at least a part ofthe software or firmware application. As yet another example, acomponent can be an apparatus that provides specific functionalitythrough electronic components without mechanical parts, the electroniccomponents can include a processor therein to execute software orfirmware that confers at least in part the functionality of theelectronic components.

In addition, the term “or” is intended to mean an inclusive “or” ratherthan an exclusive “or.” That is, unless specified otherwise, or clearfrom context, “X employs A or B” is intended to mean any of the naturalinclusive permutations. That is, if X employs A; X employs B; or Xemploys both A and B, then “X employs A or B” is satisfied under any ofthe foregoing instances. Moreover, articles “a” and “an” as used in thesubject specification and annexed drawings should generally be construedto mean “one or more” unless specified otherwise or clear from contextto be directed to a singular form.

Additionally, the terms “core-network”, “core”, “core carrier network”,“carrier-side”, or similar terms can refer to components of atelecommunications network that typically provides some or all ofaggregation, authentication, call control and switching, charging,service invocation, or gateways. Aggregation can refer to the highestlevel of aggregation in a service provider network wherein the nextlevel in the hierarchy under the core nodes is the distribution networksand then the edge networks. User equipment do not normally connectdirectly to the core networks of a large service provider, but can berouted to the core by way of a switch or radio area network.Authentication can refer to determinations regarding whether the userrequesting a service from the telecom network is authorized to do sowithin this network or not. Call control and switching can referdeterminations related to the future course of a call stream acrosscarrier equipment based on the call signal processing. Charging can berelated to the collation and processing of charging data generated byvarious network nodes. Two common types of charging mechanisms found inpresent day networks can be prepaid charging and postpaid charging.Service invocation can occur based on some explicit action (e.g., calltransfer) or implicitly (e.g., call waiting). It is to be noted thatservice “execution” may or may not be a core network functionality asthird-party network/nodes may take part in actual service execution. Agateway can be present in the core network to access other networks.Gateway functionality can be dependent on the type of the interface withanother network.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer,”“prosumer,” “agent,” and the like are employed interchangeablythroughout the subject specification, unless context warrants particulardistinction(s) among the terms. It should be appreciated that such termscan refer to human entities or automated components (e.g., supportedthrough artificial intelligence, as through a capacity to makeinferences based on complex mathematical formalisms), that can providesimulated vision, sound recognition and so forth.

Aspects, features, or advantages of the subject matter can be exploitedin substantially any, or any, wired, broadcast, wirelesstelecommunication, radio technology or network, or combinations thereof.Non-limiting examples of such technologies or networks include Geocasttechnology; broadcast technologies (e.g., sub-Hz, ELF, VLF, LF, MF, HF,VHF, UHF, SHF, THz broadcasts, etc.); Ethernet; X.25; powerline-typenetworking (e.g., PowerLine AV Ethernet, etc.); femto-cell technology;Wi-Fi; Worldwide Interoperability for Microwave Access (WiMAX); EnhancedGeneral Packet Radio Service (Enhanced GPRS); Third GenerationPartnership Project (3GPP or 3G) Long Term Evolution (LTE); 3GPPUniversal Mobile Telecommunications System (UMTS) or 3GPP UMTS; ThirdGeneration Partnership Project 2 (3GPP2) Ultra Mobile Broadband (UMB);High Speed Packet Access (HSPA); High Speed Downlink Packet Access(HSDPA); High Speed Uplink Packet Access (HSUPA); GSM Enhanced DataRates for GSM Evolution (EDGE) RAN 430 (RAN) or GERAN; Terrestrial RAN430 (UTRAN); or LTE Advanced.

What has been described above includes examples of systems and methodsillustrative of the disclosed subject matter. It is, of course, notpossible to describe every combination of components or methods herein.One of ordinary skill in the art may recognize that many furthercombinations and permutations of the disclosure are possible.Furthermore, to the extent that the terms “includes,” “has,”“possesses,” and the like are used in the detailed description, claims,appendices and drawings such terms are intended to be inclusive in amanner similar to the term “comprising” as “comprising” is interpretedwhen employed as a transitional word in a claim.

While the various embodiments are susceptible to various modificationsand alternative constructions, certain illustrated implementationsthereof are shown in the drawings and have been described above indetail. It should be understood, however, that there is no intention tolimit the various embodiments to the specific forms disclosed, but onthe contrary, the intention is to cover all modifications, alternativeconstructions, and equivalents falling within the spirit and scope ofthe various embodiments.

In addition to the various implementations described herein, it is to beunderstood that other similar implementations can be used, ormodifications and additions can be made to the describedimplementation(s) for performing the same or equivalent function of thecorresponding implementation(s) without deviating therefrom. Stillfurther, multiple processing chips or multiple devices can share theperformance of one or more functions described herein, and similarly,storage can be affected across a plurality of devices. Accordingly, theembodiments are not to be limited to any single implementation, butrather are to be construed in breadth, spirit and scope in accordancewith the appended claims.

What is claimed is:
 1. A method comprising: receiving, by networkequipment comprising a processor, a request to implement a networkservice in a network, wherein the network comprises access pointequipment connected via a transport segment to a core network segment;based on the request, selecting, by the network equipment, deploymentlocations in the network for service elements applicable to enabling thenetwork service, wherein a first service element of the service elementsis selected to be deployed at a deployment location; and facilitating,by the network equipment, deploying the first service element at thedeployment location.
 2. The method of claim 1, wherein the networkservice is implemented in a network service slice configured by thenetwork equipment to utilize resources of the network.
 3. The method ofclaim 1, wherein selecting the deployment location comprises evaluatingthe deployment locations based on requirements defined for the networkservice.
 4. The method of claim 1, wherein the service elements furthercomprise a second service element to be deployed at transport equipmentof the transport segment, and a third service element deployed at coreequipment of the core network segment.
 5. The method of claim 4, whereinthe network service comprises an encryption tunnel from the coreequipment to the access point equipment.
 6. The method of claim 5,wherein the encryption tunnel comprises a routing encapsulation tunnelthat facilitates multicast communications.
 7. The method of claim 6,wherein the first service element is deployed via a multicastcoordination function instantiated at the access point equipment.
 8. Themethod of claim 6, wherein the access point equipment couples to thetransport segment via the second service element deployed using amultiservice node virtual network function instantiated at the transportequipment.
 9. The method of claim 6, wherein the third service elementis deployed via a multicast service virtual network functioninstantiated at the core equipment.
 10. The method of claim 4, whereinthe network service comprises a control plane connection from the coreequipment to the access point equipment.
 11. The method of claim 10,wherein the third service element is deployed via an access managementvirtual network function instantiated at the core equipment, and whereinthe control plane connection comprises connections between the accesspoint equipment and the access management virtual network function. 12.The method of claim 1, further comprising: based on a first virtualnetwork function that provides the first service element not beinginstantiated at the deployment location, facilitating, by the networkequipment, instantiating the first virtual network function at thedeployment location; and configuring, by the network equipment, thefirst virtual network function to provide the first service element. 13.The method of claim 1, further comprising, based on a second virtualnetwork function that provides the first service element already beinginstantiated at the deployment location, configuring, by the networkequipment, the second virtual network function to provide the firstservice element.
 14. The method of claim 1, wherein the access pointequipment comprises wireless access point equipment, and wherein thenetwork further comprises a RAN 430 segment that provides a connectionbetween a user equipment and the wireless access point equipment. 15.Access point equipment, comprising: a processor; and a memory thatstores executable instructions that, when executed by the processor,facilitate the performance of operations, comprising: communicating arequest to a logical service system to implement a logical service in acommunications network, wherein the access point equipment is connectedby a transport section of the communications network to a core sectionof the communications network; and receiving, from the logical servicesystem, an indication that the logical service is available for use,wherein the logical service was instantiated by logical service elementsdeployed at transport equipment comprised in the transport section, andcore equipment comprised in the core section, and wherein the transportequipment and the core equipment were selected by the logical servicesystem based on a requirement of the logical service.
 16. The accesspoint equipment of claim 15, wherein communicating the request comprisesusing a multicast coordination function, and wherein the logical servicecomprises an encapsulation tunnel that provides multicast communicationsfrom the core equipment to the access point equipment.
 17. The accesspoint equipment of claim 15, wherein the operations further comprise,determining to access an access management network function at the coreequipment via a control plane connection to the core equipment, andwherein the logical service requested comprises the control planeconnection.
 18. A non-transitory machine-readable medium, comprisingexecutable instructions that, when executed by a processor, facilitateperformance of operations, comprising: monitoring elements of acommunications network for an indication that a node has enabled afeature of the communications network; based on the indication and thefeature, selecting a network service to provide the feature to the node;evaluating, based on requirements determined to be applicable to thenode, potential points in the communications network to deploy servicefunctions to provide the feature, resulting in selected deploymentpoints, wherein a first selected deployment point is comprised inside acore network of the communications network, and a second selecteddeployment point are comprised outside of the core network; anddeploying a service function of the service functions to a selecteddeployment point of the selected deployment points.
 19. Thenon-transitory machine-readable medium of claim 18, wherein the featurecomprises evolved multimedia broadcast and multicast services, andwherein the network service comprises a routing encapsulation tunnelfrom the node to a source of the multimedia broadcast and multicastservices.
 20. The non-transitory machine-readable medium of claim 18,wherein the communications network comprises at least a fifth-generationcommunication network supporting new radio communication protocols, andwherein the feature comprises access, via a control plane message, tosubscriber information from an access management function cluster.